Fixing inconsistent prev/next navigation buttons #657
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…xt one even if navigationConfig is not set/configured
Contributor
Author
|
Still not sure about this one. I think I have to go sift through the code to fully understand how these things are expected to interact with implicitly added submit button(s), etc. |
Member
|
Potential breaking change. Will be merged when we introduce V4 of App Frontend. |
Closed
|
Kudos, SonarCloud Quality Gate passed! |
19 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I've observed that the previous/next navigation buttons sometimes mysteriously disappeared, and I was about to create a bug report for it. However, to figure out if it was just my config that was wrong, I looked into it and quickly found the cause behind the problem - these buttons seem to somewhat rely on a
navigationproperty set in the layout file (which is an undocumented feature?!). I'm a bit confused about what was supposed to happen here, so I'm opening a draft PR to get some feedback. These changes seems to work in the same way the documentation describes, though.Related
Verification
Documentation